-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
QOLDEV-833 add template to stand up instances for generating golden AMIs #540
Conversation
…astructure into QOLDEV-833-autoscaling-ami
…astructure into QOLDEV-833-autoscaling-ami
- Change 'deploy' action to run 'setup' and 'deploy' recipes, but not 'configure'. This will allow us to prepare an instance but not make it active.
…for generating golden AMIs
…ov-au/ckan-qld-infrastructure into QOLDEV-833-autoscaling-ami
…astructure into QOLDEV-833-autoscaling-ami
…astructure into QOLDEV-833-autoscaling-ami
* - 'setup': Full end-to-end configuration, from vanilla operating system to live instance. | ||
* - 'deploy': Take a vanilla operating system and set up a warm instance, but do not make it active. | ||
* - 'configure': Take a warm instance and make it active. | ||
*/ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
when i see the options of
setup, deploy, configure.
I do not envision 'setup' doing everything. nor 'deploy' only making a 'warm' instance.
@chris-randall-qol and others, what is your thoughts on this.
I know this is from legacy deployPhase's we got from inheriting this codebase but i think its time to make it less confusing.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I know this is from legacy deployPhase's we got from inheriting this codebase
Yes, those were the OpsWorks terms. We could change them, it would just mean a lot of renaming.
Note that the distinction between 'deploy' and 'configure' creating warm vs hot instances did not come from OpsWorks. It's just something that I've observed to be useful if we want to make custom images.
…astructure into QOLDEV-833-autoscaling-ami
…ov-au/ckan-qld-infrastructure into QOLDEV-833-autoscaling-ami
- Apply disk size adjustments for Solr servers - Reuse Lambda function and IAM role
its coming together, so now we can boot up a blank server and get it python installed etc. we now need in ansible to take ami it and then set paramstore of the ami it made so that it can be picked up and injected into the asg groups in the next step for ensuing new instances are using 'current' for quick boot times. ie. heres some pseudo code that is the direction i'd think it could go. (your welcome to go another direction)
then in asg cfn template section, do lookup for param and update to use that (else fall back to vanilla) |
…astructure into QOLDEV-833-autoscaling-ami
No description provided.